home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
The CICA Windows Explosion!
/
The CICA Windows Explosion! - Disc 2.iso
/
nt
/
ntkb.zip
/
NTKB.EXE
/
Q108
/
5
/
05.TXT
< prev
next >
Wrap
Text File
|
1993-12-20
|
3KB
|
74 lines
DOCUMENT:Q108505 17-DEC-1993 [W_NT]
TITLE :Disconnecting from a Trusted Domain Network
PRODUCT :Windows NT
PROD/VER:3.10
OPER/SYS:WINDOWS
KEYWORDS:
--------------------------------------------------------------------------
The information in this article applies to:
- Microsoft Windows NT operating system version 3.1
- Microsoft Windows NT Advanced Server version 3.1
--------------------------------------------------------------------------
SYMPTOMS
========
If you have a Windows NT computer that participates in a trusted domain
structure that is sometimes disconnected from the main network, you may
experience problems accessing it from another computer when it is
disconnected from the main network.
An example of this scenario is the following:
A field engineer has two computers. One computer runs Windows NT and
participates in a trusted domain. The other computer runs Windows for
Workgroups. The computer running Windows for Workgroups is connected to the
Windows NT computer, but the computer running Windows NT is not connected
to the main network. Accessing the Windows NT computer from the Windows for
Workgroups computer can result in the following error message:
Access Denied
The Windows NT computer will look for the Domain Controller when it is
accessed and it cannot find one, so it returns the above error message.
WORKAROUND
==========
When you are not connected to the main network, you can change the Windows
NT computer to be a member of a workgroup instead of a member of a domain.
You can do this with the Network applet in Control Panel.
Now the Windows NT computer will not look for the Domain Controller. You
must have a user with the permissions you want defined in the local account
database or this will not work.
DonÆt forget to rejoin the domain you were in when the Windows NT computer
is reconnected to the main network.
Microsoft has confirmed this to be a problem in Microsoft Windows NT and
Windows NT Advanced Server version 3.1. We are researching this problem and
will post new information here in the Microsoft Knowledge Base as it
becomes available.
Additional reference words: 3.10
KBCategory:
KBSubCategory: netsrv
=============================================================================
THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS
PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS
ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES
OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO
EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR
ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL,
CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF
MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE
POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION
OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES
SO THE FOREGOING LIMITATION MAY NOT APPLY.
Copyright Microsoft Corporation 1993.